home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Click Art Business Graphics
/
ClickArt - Business Graphics.iso
/
CPIC32
/
MCI.TXT
< prev
next >
Wrap
Text File
|
1998-09-09
|
9KB
|
221 lines
----------------------------------------------------------------------
CPIC version 1.80 (build 273) - Released April 20, 1998
----------------------------------------------------------------------
Note for PhotoSAFE users
========================
PhotoSAFE is a custom version of CPIC which has been
combined with DataSAFE. All references to CPIC here
also refer to the PhotoSAFE viewer.
======================================================================
How to Find, Install and Test Multimedia MCI Drivers
======================================================================
MPEG NOTE: Microsoft Corporation has announced new support for MPEG,
which is to be coming soon. Currently, the only MPEG drivers Photodex
has been able to find are buggy and not recommended. When Microsoft
releases their MPEG drivers, Photodex will make them available if
possible and provide installation instructions.
======================================================================
========================
WHERE TO GET MCI DRIVERS
========================
You can download freeware/shareware MCI drivers from all major on-line
sources. For each of the on-line services, follow the instructions on
how to download each type of MCI driver.
COMPUSERVE (WINCIM)
------------------------------
VIDEO FOR WINDOWS (.AVI files)
------------------------------
1) GO WINMM (This is the MS Win Multimedia Forum.)
2) Select 'Browse' from the 'Library' menu.
3) Select the 'Video for Windows' library (Library 4.)
4) Find the file called 'VFW 1.1e Runtime' (VFW11E.ZIP)
and download. (The file should be stored in the
C:\CSERVE\DOWNLOAD directory, unless you have the
WinCIM software installed elsewhere.)
5) Proceed to INSTALLING VIDEO FOR WINDOWS below.
---------------------------------
QUICKTIME MCI DRIVER (.MOV files)
---------------------------------
NOTE: 32-bit QuickTime will NOT work. Apple is working on this.
1) GO QTW (This is the BAMUG forum on CompuServe.)
2) Download the file QTINSTAL.EXE and follow the installation
instructions. (The file should be stored in the path called
C:\CSERVE\DOWNLOAD directory, unless you have the WinCIM
software installed elsewhere.)
3) Proceed to INSTALLING QUICKTIME below.
-----------------------------------------------
AUTODESK ANIMATION (.FLI, .FLC, and .FLX files)
-----------------------------------------------
1) GO PHOTODEX (This is the Photodex Forum.)
2) Select 'Browse' from the 'Library' menu.
3) Select the 'VIEWERS (CPIC, GDS)' library (Library 3.)
4) Find the file called 'MCI Driver: FLI/FLC/FLX'
(AAWIN11.EXE) and download. (The file should be
stored in the C:\CSERVE\DOWNLOAD directory, unless
you have the WinCIM software installed elsewhere.)
5) Proceed to INSTALLING AUTODESK ANIMATION below.
INTERNET (World Wide Web)
--------------
ALL FILE TYPES
--------------
NOTE: 32-bit QuickTime will NOT work. Apple is working on this.
Using the world wide web, go to http://www.photodex.com.
This link includes drivers and links to the following
drivers: VMPEG.EXE (.MPG) Autodesk Animation (.FLI, .FLC,
.FLX) QuickTime (.MOV) and Video For Windows (.AVI).
You may also want to search the web for other MPEG drivers
including Xing and NetToob.
AMERICA ONLINE
------------------------------
VIDEO FOR WINDOWS (.AVI files)
------------------------------
Search the Software Libraries for VFW11E.ZIP
---------------------------------
QUICKTIME MCI DRIVER (.MOV files)
---------------------------------
NOTE: 32-bit QuickTime will NOT work. Apple is working on this.
Search the Software Libraries for QT16.EXE
-----------------------------------------------
AUTODESK ANIMATION (.FLI, .FLC, and .FLX files)
-----------------------------------------------
Search the Software Libraries for AAWIN.ZIP
==========================
HOW TO INSTALL MCI DRIVERS
==========================
Follow the instructions below to install each type of MCI driver.
------------------------------
VIDEO FOR WINDOWS (.AVI files)
------------------------------
1) Create a directory to hold the setup program for Video for Windows.
2) Copy VFW11E.ZIP to the directory you created.
3) In a DOS shell (or WinZIP), log to the directory you created and
use PKUNZIP to decompress the VFW11E.ZIP file. To do this, use,
the following DOS command line:
PKUNZIP VFW11E.ZIP
4) Exit the DOS shell (or WinZIP) and return to the Windows.
5) Use File Manager to execute the SETUP.EXE file in the directory you
created.
6) Follow the on-screen instructions to install Video for Windows.
----------------------
QUICKTIME (.MOV files)
----------------------
NOTE: 32-bit QuickTime will NOT work. Apple is working on this.
1) Follow the instructions given by Apple in the QuickTime download
area.
-----------------------------------------------
AUTODESK ANIMATION (.FLI, .FLC, and .FLX files)
-----------------------------------------------
1) Use File Manager to create a new directory and copy the AAWIN11.EXE
file into this new directory.
2) Use File Manager to execute the AAWIN11.EXE program. This will expand
the setup files.
3) Use File Manager to copy the MCIAAP.DRV file and all other DLL files
in the directory to your \WINDOWS\SYSTEM directory.
4) Edit the SYSTEM.INI file in your \WINDOWS directory and add the
following line to the [mci] section (do NOT include the '-->'
arrow on the left, it's there to show you which line.):
[mci]
...
--> Animation1=mciaap.drv
...
5) Edit the CONTROL.INI file in your \WINDOWS directory and add the
following line to the [drivers.desc] section (do NOT include the
'-->' arrow on the left, it's there to show you which line.):
[drivers.desc]
...
--> mciaap.drv=[MCI] Autodesk Animation 1.10
...
6) Edit the WIN.INI file in your \WINDOWS directory and add the
following line to the [mci extensions] section (do NOT include
the '-->' arrow on the left, it's there to show you which line.):
[mci extensions]
...
--> fli=Animation1
flc=Animation1
...
7) Exit and restart Windows.
=======================
HOW TO TEST MCI DRIVERS
=======================
Windows MCI drivers are the most common way to support multimedia files.
Unfortunately, many MCI drivers still have bugs, and these bugs can cause
all kinds of glitches when CPIC attempts to support them.
CPIC has been extensively tested with commonly available MCI drivers and has
worked very reliably. Before you suspect that CPIC is the problem, please
verify that the MCI driver for the type of file you're trying to play works
with the Microsoft Windows Media Player (MPLAYER.EXE in the Windows folder.)
-------------------
TO RUN MEDIA PLAYER
-------------------
1) Using the File manager, locate the file called MPLAYER.EXE or
MPLAY32.EXE.
2) Double click on the media player executable file to execute it.
---------------------
TO TEST AN MCI DRIVER
---------------------
1) Select 'Open' from the 'File' menu and find a file to test. You
can tell the file type by the file's extension (AVI, MOV, MPG,
WAV, MID, RMI, FLI, etc.)
2) Click on the "double right arrows" button to start the file
playing. If the file plays, then it is possible to set the CPIC
options so the MCI driver is supported.
IF FILES PLAY IN THE MEDIA PLAYER
---------------------------------
If files play using Media Player but do NOT play using CPIC, then the
problem has to do with a bug in the MCI that is being aggravated by an
Options setting in CPIC. Run CPIC, and select the Multimedia option in
the Options menu. Modify the settings for the file type and see which
combination works.
Note that in some instances, the MCI driver will crash CPIC, Windows or
even both. If Windows crashes, you'll have to restart. Make sure that
options which you know crash with your MCI driver are NOT set.
If an MCI driver crashes CPIC but does NOT crash Windows, you will need
to exit and restart Windows before CPIC will run again. This is
because part of CPIC stays in memory when the MCI driver blows up, and
the only way to remove it is to restart Windows.
IF FILES DO NOT PLAY IN THE MEDIA PLAYER
----------------------------------------
There is something wrong with the MCI driver itself or the way the MCI
driver has been installed. Consult the documentation which came with the
MCI driver for details. Call the companies that made the MCI driver and
ask for assistance using their software.